Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

🏁 Script executed:

#!/bin/bash
# Check repository structure
echo "=== Repository Structure ==="
ls -la

# Check package.json content
echo -e "\n=== Package.json Content ==="
cat package.json

# Check ESLint config
echo -e "\n=== ESLint Config ==="
cat eslint.config.js 2>/dev/null || echo "eslint.config.js not found"

# Check Yarn configuration
echo -e "\n=== Yarn Configuration ==="
cat .yarnrc.yml 2>/dev/null || echo ".yarnrc.yml not found"

# Check if the package exists in node_modules
echo -e "\n=== Check for @1stg/eslint-config ==="
find . -path "*@1stg/eslint-config*" 2>/dev/null || echo "Package not found in standard location"

# Check Yarn version
echo -e "\n=== Yarn Version ==="
cat .yarn/releases/* 2>/dev/null | grep -i "yarnpkg" | head -n 5 || echo "Yarn release info not found"

Length of output: 75859

🏁 Script executed:

#!/bin/bash
# Check more about the directory structure and dependencies
echo "=== Looking for @1stg/eslint-config in node_modules ==="
find . -name "node_modules" -type d -exec ls -la {} \; 2>/dev/null

# Check the changed files in the PR
echo -e "\n=== PR Changed Files ==="
cat src/run.ts

# Check if @1stg/eslint-config is a dependency of @1stg/common-config
echo -e "\n=== Checking package dependencies ==="
ls node_modules/@1stg 2>/dev/null || echo "No @1stg folder in node_modules"

# Check the changeset file
echo -e "\n=== Changeset File ==="
cat .changeset/ten-eagles-sing.md 2>/dev/null || echo "Changeset file not found"

Length of output: 10666